Lucene search

K
OctopusOctopus Deploy

5 matches found

CVE
CVE
added 2020/03/19 3:15 p.m.43 views

CVE-2020-10678

In Octopus Deploy before 2020.1.5, for customers running on-premises Active Directory linked to their Octopus server, an authenticated user can leverage a bug to escalate privileges.

8.8CVSS8.6AI score0.00768EPSS
CVE
CVE
added 2018/01/03 9:29 a.m.42 views

CVE-2018-4862

In Octopus Deploy versions 3.2.11 - 4.1.5 (fixed in 4.1.6), an authenticated user with ProcessEdit permission could reference an Azure account in such a way as to bypass the scoping restrictions, resulting in a potential escalation of privileges.

8.8CVSS8.6AI score0.00192EPSS
CVE
CVE
added 2018/01/16 10:29 a.m.36 views

CVE-2018-5706

An issue was discovered in Octopus Deploy before 4.1.9. Any user with user editing permissions can modify teams to give themselves Administer System permissions even if they didn't have them, as demonstrated by use of the RoleEdit or TeamEdit permission.

8.8CVSS8.5AI score0.00196EPSS
CVE
CVE
added 2017/12/13 8:29 p.m.34 views

CVE-2017-17665

In Octopus Deploy before 4.1.3, the machine update process doesn't check that the user has access to all environments. This allows an access-control bypass because the set of environments to which a machine is scoped may include environments in which the user lacks access.

8.8CVSS8.6AI score0.00269EPSS
CVE
CVE
added 2019/05/01 2:29 p.m.32 views

CVE-2019-11632

In Octopus Deploy 2019.1.0 through 2019.3.1 and 2019.4.0 through 2019.4.5, an authenticated user with the VariableViewUnscoped or VariableEditUnscoped permission scoped to a specific project could view or edit unscoped variables from a different project. (These permissions are only used in custom U...

8.1CVSS7.8AI score0.00348EPSS